Agile Prototyping A combination of different approaches into one main process
نویسنده
چکیده
Software prototyping is considered to be one of the most important tools that are used by software engineers nowadays to be able to understand the customer’s requirements, and develop software products that are efficient, reliable, and acceptable economically. Software engineers can choose any of the available prototyping approaches to be used, based on the software that they intend to develop and how fast they would like to go during the software development. But generally speaking all prototyping approaches are aimed to help the engineers to understand the customer’s true needs, examine different software solutions and quality aspect, verification activities...etc, that might affect the quality of the software underdevelopment, as well as avoiding any potential development risks. A combination of several prototyping approaches, and brainstorming techniques which have fulfilled the aim of the knowledge extraction approach, have resulted in developing a prototyping approach that the engineers will use to develop one and only one throwaway prototype to extract more knowledge than expected, in order to improve the quality of the software underdevelopment by spending more time studying it from different points of view. The knowledge extraction approach, then, was applied to the developed prototyping approach in which the developed model was treated as software prototype, in order to gain more knowledge out of it. This activity has resulted in several points of view, and improvements that were implemented to the developed model and as a result Agile Prototyping AP, was developed. AP integrated more development approaches to the first developed prototyping model, such as: agile, documentation, software configuration management, and fractional factorial design, in which the main aim of developing one, and only one prototype, to help the engineers gaining more knowledge, and reducing effort, time, and cost of development was accomplished but still developing software products with satisfying quality is done by developing an evolutionary prototyping and building throwaway prototypes on top of it.
منابع مشابه
Institutionen För Datavetenskap a Combination of Different Approaches into One Main Process a Combination of Different Approaches into One Main Process Dedicated to My Mother's Soul and Memory
_______________________________________________________________________
متن کامل9 Agile Interaction Design and Test-Driven Development of User Interfaces – A Literature Review
This chapter describes the development of GUI-based applications, from usability engineering and prototyping to acceptance test-driven development, in an agile context. An overview of current agile interaction design practices will be presented, including a thorough analysis of the current role of prototyping and current attempts to facilitate test-driven development of GUI systems, as presente...
متن کاملnO.Wld~d~Je-llla~~ed system for choice of rapid prototyping process
product development processes are not limited to layer-manufacturing machines, but they also integrate reverse engineering, indirect methods for metallic and plastic part manufacturing, etc... Due to short delays, people have no time to test and compare different solutions of rapid product development processes. Even people have time, tests are time and money consuming. It is also very difficul...
متن کاملAn Agile BPM Project Methodology
Business Process Management (BPM) has become one of the most important management disciplines in recent years. In reality, however, many technical process improvement projects failed in the past and the expected benefits could not be established. In the meantime, the agile software development movement made massive progress in contrast to classic waterfall approaches which are still the foundat...
متن کاملTowards Agile Model-Driven Web Engineering
The increasing growth of the Web field has promoted the development of a plethora of Model-Driven Web Engineering (MDWE) approaches. These methodologies share a top-down approach: they start by modeling application content, then they define a navigational schema, and finally refine the latter to obtain presentation and rich behavior specifications. Such approach makes it difficult to acquire qu...
متن کامل